Thank you for the feedback! I will work on that shortly.

I've tried my best to spend a bit of time unpacking this. Ultimately, I didn't think it was best to include all types of Index in the overload because not all types of Index are valid to union with MultiIndex (only those with tuples). Referring to tuples within Indexes wasn't supported so I had to add that support in _typing.pyi.

Happy to adjust recognising that Dr-Irv never mentioned any issue with using the complete Index type.

Additionally, I've attempted to add a test in tests/indexes/test_indexes.py covering the different cases I could think of.

I can see now that all checks have failed, looks related to my extension of S1 (in adding support for tuple[Hashable, ...] I seem to have violated some sort of constraint). Any guidance would be greatly appreciated.

Ended up removing MultiIndex-Index unions from assumption for returning a MultiIndex - was causing too many problems and Dr-Irv said it was okay to ignore. It was either violating the overload standard or confusing mypy in testing.

swaplevel tests added, MultiIndex tests removed some cases relating to different types of Indexes (since we no longer try checking for those), and S1 changes reverted.

I'm not sure why it failed. I ran poe test_all locally several times; all successful.

Running the test case locally individually it failed, seems to be a runtime error because Pandas won't accept an Index unionising a MultiIndex (as it should). Removing that test case.

Please also run pre-commit locally.

My mistake. I had ran a pre-commit after committing, and didn't commit the refactoring it made.

• In addition please also fix mypy type checking and further poe checks.

Removing the overload of union from the MultiIndex class and instead setting MultiIndex to return Self caused a few existing tests to fail. I would prefer to reinstate the overload to maintain the existing test behaviour, but I could alternatively just modify the existing tests.

Which would you prefer?

I believe your changes actually improve the typing in the exising tests, if you take a look. So you can update the static and runtime typing checks in the tests.

In the stubs file for RangeIndex, you can try to ignore the error, or use @override.

In the stubs file for RangeIndex, you can try to ignore the error, or use @override.

@override did not work unfortunately - how do I ignore the error; is this even permitted?

Edit: Nevermind, figured out how to ignore the error.

I don't understand. poe test_all passes on my machine. Does it not cover the same test suite? The errors appear to be runtime-based.

Thank you @realzachbrownjohn ! I hope you enjoyed your first PR.

Thank you for your help! I did!